Ensure CNAME file is copied over to built docs site #2446
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
documentation
istride
force-pushed
the
fix-cname-part-2
branch
from
647bf13
to
61efad6
Compare
The github action that deploys the docs site tries to create a CNAME file in a directory that doesn't yet exist, and fails. Alternative is to just create a CNAME file in 'documentation/docs', where it will be copied over to the final site.
ChrisMarsh82
approved these changes
Oct 2, 2024
istride
force-pushed
the
fix-cname-part-2
branch
from
61efad6
to
58ac571
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The github action that deploys the docs site tries to create a CNAME file in a directory that doesn't yet exist, and fails. Alternative is to just create a CNAME file in 'documentation/docs', where it will be copied over to the final site.